Skip to content

fix: bump RAM for listed-building - #90

Draft
tombrooks248 wants to merge 1 commit into
mainfrom
fix/bump-listed-building-ram
Draft

fix: bump RAM for listed-building#90
tombrooks248 wants to merge 1 commit into
mainfrom
fix/bump-listed-building-ram

Conversation

@tombrooks248

@tombrooks248 tombrooks248 commented Jul 10, 2026

Copy link
Copy Markdown
Contributor

What type of PR is this? (check all applicable)

  • Refactor
  • Feature
  • Bug Fix
  • Optimization
  • Documentation Update

Why has this not been implemented

On Friday the 10th this listed-building failed with the error described below, but after a rerun it actually ran cleanly. Given we are going to move these pipelines to pyspark soon, I've decided to drop this work for now, but keeping the PR in case we see this error again before pyspark can be implemented.

Description

Add a memory: 65536 (64 GiB) override to the listed-building / tree-preservation-order
branch in dag_triggers.py (both the scheduled and manual master DAGs).

Why

listed-building-assemble-and-bake failed overnight with a DuckDB out-of-memory error during load_entities_range:

duckdb.duckdb.OutOfMemoryException: failed to pin block of size 4.2 MiB (25.5 GiB/25.5 GiB used)

These two collections already get a CPU bump (16 vCPU) via this branch, but memory stayed at the 32 GiB default, which is the Fargate minimum for 16 vCPU. DuckDB caps itself at 80% of container RAM (25.5 GiB) and hit that ceiling. Root cause is data growth (listed-building now ~387k entities)

Raising to 64 GiB gives DuckDB ~51 GiB usable (2× headroom). 16 vCPU permits up to 120 GiB
if we need to go further.

Which pipelines get affected

  • Affects listed-building and tree-preservation-order (they share this branch in airflow which gets compute from fargate).

Related Tickets & Documents

  • Ticket Link
  • Related Issue #
  • Closes #

QA Instructions, Screenshots, Recordings

Please replace this line with instructions on how to test your changes, a note
on the devices and browsers this has been tested on, as well as any relevant
images for UI changes.

Added/updated tests?

We encourage you to keep the code coverage percentage at 80% and above. Please refer to the Digital Land Testing Guidance for more information.

  • Yes
  • No, and this is why: we are just configuring airflow not introducing any new features.
  • I need help with writing tests

[optional] Are there any post deployment tasks we need to perform?

[optional] Are there any dependencies on other PRs or Work?

@tombrooks248
tombrooks248 marked this pull request as ready for review July 10, 2026 08:04
@tombrooks248
tombrooks248 force-pushed the fix/bump-listed-building-ram branch from 335b87c to 501fb65 Compare July 10, 2026 09:21
@tombrooks248
tombrooks248 marked this pull request as draft July 10, 2026 09:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant